Mitigating communication risk by detecting similarity to a trusted message contact

ABSTRACT

At least one of a measure of trust or a measure of spoofing risk associated with a sender of a message is determined. A measure of similarity between an identifier of the sender of the message and an identifier of at least one trusted contact of a recipient of the message is determined. The measure of similarity is combined with at least one of the measure of trust or the measure of spoofing risk to at least in part determine a combined measure of risk associated with the message. Based at least in part on the combined measure of risk associated with the message, a verification action is performed including by automatically providing an inquiry message that requests a response to be provided.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/207,139 entitled MITIGATING COMMUNICATION RISK BY DETECTING SIMILARITY TO A TRUSTED MESSAGE CONTACT filed Mar. 19, 2021, which is a continuation of U.S. patent application Ser. No. 16/399,801 entitled MITIGATING COMMUNICATION RISK BY DETECTING SIMILARITY TO A TRUSTED MESSAGE CONTACT filed Apr. 30, 2019, now U.S. Pat. No. 10,992,645, which is a continuation of U.S. patent application Ser. No. 15/723,524, now U.S. Pat. No. 10,326,735 entitled MITIGATING COMMUNICATION RISK BY DETECTING SIMILARITY TO A TRUSTED MESSAGE CONTACT filed Oct. 3, 2017, which is a continuation of U.S. patent application Ser. No. 15/453,737, now U.S. Pat. No. 9,847,973 entitled MITIGATING COMMUNICATION RISK BY DETECTING SIMILARITY TO A TRUSTED MESSAGE CONTACT filed Mar. 8, 2017, which claims priority to U.S. Provisional Patent Application No. 62/399,821 entitled MITIGATING COMMUNICATION RISK filed Sep. 26, 2016, all of which are incorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

Deception is rapidly on the rise on the Internet, and email is the attack vector of choice for a broad array of attacks, including ransomware distribution, enterprise-facing cons, and mass-deployed phishing attacks. It is widely believed that this is due to the ubiquity of email and the limited extent to which relevant email security measures have been rolled out. One of the most troubling types of attack is the targeted attack, in which the attacker poses as somebody the intended victim knows.

There are three common ways used by attackers to masquerade as somebody trusted: spoofing, look-alike domain attacks, and display name attacks (collectively referred as impersonation attacks). In a spoofing attack, an email is injected in the mail stream (commonly at an open relay controlled by the adversary) with manipulated headers indicating that the email was sent by a party known to the recipient. Look-alike domain attacks (also referred to as cousin-name attacks) involve the attackers registering deceptive domains and sending emails from these. An example look-alike domain is bankofarnerica.com (notice the use of “rn” instead of “m” in the name). In a display name attack, the adversary simply sets the display name of an account he controls (commonly a throw-away webmail account) to match the display name of the party the attacker wishes to impersonate. To make it concrete, a typical email of this type may be sent from “Bank of America <janeroe104@gmail.com>”, where the display name is “Bank of America” and the associated email address is <janeroe104@gmail.com>. Since the display name is commonly the only indication of the identity of the sender that is displayed to the recipient (and almost always the only one that the recipient pays attention to), this attack is very effective.

Therefore, there exists a need for effective ways to detect and handle impersonation attacks.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.

FIG. 1 is a diagram illustrating an embodiment of a system environment for analyzing a message.

FIG. 2 is a flowchart illustrating an embodiment of a process for tracking trusted contacts.

FIG. 3 is a flowchart illustrating an embodiment of a process for determining information about a message sender to be utilized to assess a risk of a message.

FIG. 4 is a flowchart illustrating an embodiment of a process for determining a total risk measure of a contact.

FIG. 5 is a flowchart illustrating an embodiment of a process for assessing a received message for filtering.

FIG. 6A is a flowchart illustrating an embodiment of a process for modifying a display name of a sender of the message.

FIG. 6B is a flowchart illustrating an embodiment of a process for modifying a reply address of a sender of the message.

FIG. 7 is a flowchart illustrating an embodiment of a process for securing a message.

FIG. 8A is a flowchart illustrating an embodiment of a process for detecting misrecognition of a sender of a message by a recipient of the message.

FIG. 8B shows an example of a modified message requesting manual classification of the sender of the message.

FIG. 9A is a flowchart illustrating an embodiment of a process for requiring a sender of a message to verify an identity of the sender.

FIG. 9B shows an example of an automatic reply message requesting verification of an identity of the sender of the message.

FIG. 10 is a flowchart illustrating an embodiment of a process for determining a change in historical reputation of a sender of a message.

FIG. 11 is a flowchart illustrating an embodiment of a process for linking a secondary message account of a user.

FIG. 12 is a flowchart illustrating an embodiment of a process for detecting an account take over.

FIG. 13 is a flowchart illustrating an embodiment of a process for detecting forwarding of a message.

FIG. 14 is a flowchart illustrating an embodiment of a process for detecting message bomb attacks.

FIG. 15 is a flowchart illustrating an embodiment of a process for providing a secure message interaction interface region.

FIG. 16A shows example components of a message and FIG. 16B shows a secure display area of the message.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.

Analyzing received messages is disclosed. For example, the message is an email message received for delivery to a recipient and the message is to be analyzed to detect whether the message is suspicious and is a part of an impersonation attack. The message may be suspicious due to content of the message (e.g., malware email attachment, includes a link to a phishing website, etc.) and/or a sender of the message (e.g., display name of the sender does not match sender email address).

In some embodiments, a measure of similarity between a sender identifier of the message and each identifier of each trusted contact of a plurality of trusted contacts of a recipient of the message is determined. For example, a list of trusted contacts of a recipient of the message is maintained by a system analyzing risk of incoming messages. This system may track trusted contacts of members of an organization (e.g., for each email user of a domain) for each member individually and/or together as a group. The list of trusted contacts may be at least in part specified by a user. For example, the user provided the system access to an address book of the user. In some embodiments, at least a portion of the trusted contacts is determined automatically. For example, based on observed recipients and senders of message traffic received and sent by the user, at least a portion of the trusted contacts is generated automatically. By determining the measure of similarity, a risk of likelihood of confusion by the message recipient that the message is from a trusted contact of the user is able to be determined. An example of the measure of similarity is a string distance between an email address or a display name of the sender of the message and an email address or an associated display name of a trusted contact.

In the event the sender of the message is not any of the trusted contacts but at least one of the measures of similarity meets a threshold, the message is filtered, if applicable. For example, if the email address of the sender matches an email address of a trusted contact, the message is to be trusted and not filtered but if the email address of the sender does not match any trusted contacts but is similar to an email address of a trusted contact, the message is identified as potentially a part of an impersonation attack. Filtering the message may include blocking the message, quarantining the message, further analyzing the message, and/or modifying the message to alter a data field of the message including an identification of the sender of the message (e.g., modify to insert a warning).

In some embodiments, in response to a determination that the message is suspicious (e.g., first risk analysis results in a determination that the message meets a first criteria), additional risk analysis is performed (e.g., perform a second risk analysis). For example, if the message is suspicious, at least a portion of the message is modified prior to sending a modified version of the message to a specified recipient of the message and a second risk analysis of the message is performed. The analysis of determining that the message is suspicious (e.g., first risk analysis) is performed before sending the modified version of the message and the modified version of the message is sent to the specified recipient of the message prior to a conclusion of the second risk analysis. For example, the modified version of the message is sent and delivered to a server mailbox of the specified recipient of the message prior to the conclusion of the second risk analysis.

In some embodiments, a recipient of the message is sent an inquiry requesting the recipient to verify which sender is believed to have sent the message prior to allowing full access to the message (e.g., ask recipient if the email address and/or display name of the message is someone that the recipient knows). In the event the second risk analysis results in a determination that the message meets a second criteria, the specified recipient of the message is provided content of the message that was previously prevented from being accessed by the specified recipient.

FIG. 1 is a diagram illustrating an embodiment of a system environment for analyzing a message. Examples of the message include an electronic mail (i.e., email), an instant message, a text message, a Short Message Service (SMS) message, a text message, a Multimedia Messaging Service (MMS) message, and any other forms of electronic messages. Analysis server 102 is connected to recipient message server 106 via network 108. In some embodiments, analysis server 102 is directly embedded or implemented in recipient message server 106. Sending message server 104 sends a message to recipient message server 106 for delivery to a recipient associated with recipient message server 106. In some embodiments, recipient message server 106 is a local message server. Gateway 110 receives the message prior to delivery to recipient message server 106. Gateway 110 may process incoming email messages for one or more recipient users of an organization (e.g., for users with a common domain email address). In various embodiments, recipient message server 106 may be any type of server that receives a message for delivery to a recipient user. Sending message server 104 is the last server that handled a message prior to delivery to recipient message server 106 via network 108. For example, sending message server 104 is an outgoing email server of a sender of the message. In various embodiments, sending message server 104 may be any type of server able to send a message to recipient message server 106.

Analysis server 102 processes a received message and filters it for potentially harmful or undesired messages. For example, incoming messages are filtered and analyzed for spam, viruses, spoofing, impersonation, and any other harmful or undesired content to detect, prevent, or minimize such messages from reaching a message recipient served by the recipient message server. In some embodiments, analysis server 102 determines and/or maintains a list of trusted contacts for one or more users (e.g., user accounts) of recipient message server 106. For example, by obtaining an address book from a user and/or observing message traffic to and from server 106 of the user, server 102 determines and/or maintains a list for each user.

In some embodiments, a message sent from sending message server 104 is first received at analysis server 102 prior to being received at gateway 110 and recipient message server 106. In some embodiments, a message sent from sending message server 104 is first received at gateway 110 that sends the message to analysis server 102. In some embodiments, a message sent from sending message server 104 is received at gateway 110 that sends the message to recipient message server 106 and recipient message server 106 send the message to analysis server 102. In an alternative embodiment, analysis server 102 is included in gateway 110. In an alternative embodiment, analysis server 102 is included in message server 106.

In addition to analyzing the message, analysis server 102 may block and/or modify the message or instruct another server (e.g., instruct server 106) to block and/or modify the message in the event a potential threat is detected. In some embodiments, analysis server 102 initiates a user inquiry regarding a sender of the message in the event a potential threat is detected. In some embodiments, analysis server 102 receives information about one or more messages sent by a user of message server 106 (e.g., receives the message or a portion of the message, a recipient identifier included in the message, etc.). This information may be utilized by analysis server 102 to identify message behavior and/or message contacts of the user.

In some embodiments, recipient message server 106 performs a risk analysis for an incoming message at least in part by performing an authenticity and/or reputation analysis to determine an overall measure of risk (e.g., risk score). Performing authenticity analysis may include determining a measure of confidence that a sender identified in the message (e.g., domain of sender) is the actual sender of the message. Performing reputation analysis may include determining a measure that an identified sender of the email (e.g., domain of sender) is likely to send a message that is of value to a recipient (e.g., likelihood of sending message that a recipient would want/desire to receive).

In some embodiments, determining authenticity of a message includes utilizing sender profiles that link an identifier of a sender to one or more IP addresses of servers determined to be associated with the sender. These sender profiles may be determined by analysis server 102 and/or the determined results are accessed by recipient message server 106 from analysis server 102 via network 108. For example, analysis server 102 is in communication with a plurality of different recipient message servers and analysis server 102 at least in part automatically determines associations between sender identifiers (e.g., network/Internet domain, email address, etc.) and IP addresses by analyzing messages that have been received at one or more recipient message servers. In some embodiments, a sender model of a sender may be specifically determined for a particular recipient (e.g., specific for all recipients of a particular domain, particular for an individual recipient, etc.). For example, a sender may only utilize a specific server with a first IP address for one group of recipients (e.g., recipients geographically located in North America) while another server with a second IP address is only utilized for another group of recipients (e.g., recipients geographically located in Asia).

In some embodiments, determining a reputation of a sender of a message includes utilizing a predetermined database of senders and their associated reputations. The reputations of senders may be determined by analysis server 102 and/or the determined reputations are accessed by recipient message server 106 from analysis server 102 via network 108. For example, analysis server 102 is in communication with a plurality of different recipient message servers and the analysis server 102 at least in part automatically determines a reputation score for a sender (e.g., network/Internet domain, email address, etc.) at least in part by using machine learning to analyze messages from the sender that have been received at one or more recipient message servers. In some embodiments, a reputation of a sender may be specifically determined for each particular message recipient (e.g., specific for all recipients of a particular domain, particular for an individual recipient, etc.). For example, a measure of reputation for a sender may be different for each different message recipient based on whether the recipient has had a prior communication relationship with the sender.

In some embodiments, the risk analysis performed by recipient message server 106 results in a risk value corresponding to the combination of the authenticity and reputation measures of the message. The risk value may be utilized at least in part to flag/label the message and/or to determine whether to allow the message to be delivered to an intended recipient of the message.

Examples of network 108 include one or more of the following: a direct or indirect physical communication connection, a mobile communication network, Internet, intranet, Local Area Network, Wide Area Network, Storage Area Network, and any other form of connecting two or more systems, components, or storage devices together. Other communication paths may exist and the example of FIG. 1 has been simplified to illustrate the example clearly. Although single instances of many of the components shown in FIG. 1 have been shown to simplify the diagram, additional instances of any of the components shown in FIG. 1 may exist. For example, a plurality of recipient message servers are connected and/or managed by analysis server 102. Multiple analysis servers may exist. Multiple recipient message servers may serve the same recipient entity/domain. Components not shown in FIG. 1 may also exist. Any of the components shown in FIG. 1 may be a logical, physical, or virtual component.

FIG. 2 is a flowchart illustrating an embodiment of a process for tracking trusted contacts. The process of FIG. 2 may be at least in part performed by analysis server 102, gateway 110 and/or message server 106 of FIG. 1 . Examples of the contacts include email addresses, usernames, display names, user identifiers, an identification photo, and any other identifier that may be utilized to identify a sender or recipient of a message.

At 202, trusted contacts for a user are determined. The trusted contacts are to be utilized to identify potential message threats of the user. The trusted contacts identify one or more contacts (e.g., senders or recipients of messages) that are familiar to the user because the user has previously interacted with the contact and/or is aware of the contact. In some embodiments, determining the trusted contacts includes receiving a list of contacts for the user. For example, the user provides access to an address book of the user and information about contacts in the address book is received. In some embodiments, the trusted contacts include contacts that have been specifically identified by the user. In some embodiments, information about the trusted contacts is stored. For example, the trusted contacts for the user are stored in a database of trusted contacts. This database may track trusted contacts for a plurality of different users and allows trusted contacts to be retrieved for a specific identified user. The stored information of each contact may include one or more of the following: email address, associated name (e.g., display name), relationship identifier, identifying image (e.g., contact photo), username, instant message identifier, address, phone number, a measure of trust, a measure of message interaction, and any other identifier utilized to identify a sender or a receiver of a message.

In some embodiments, the trusted contacts for the user are at least in part determined automatically based on contacts detected in messages sent or received by the user. For example, by observing and analyzing message traffic of the user and patterns of message recipients and senders, contacts that receive messages from the user and contacts that send messages to the user can be determined and correlated to infer and determine trust, frequency, and/or importance of interaction and relationship between the user and the contact to identify one or more of these contacts as a trusted contact. In one example, if a threshold number of messages has been sent to and from a contact for a user, the contact is identified as a trusted contact and added to a stored list of trusted contacts for the user. Information about the messages of the user utilized to at least in part automatically determine the trusted contacts has been obtained for analysis by receiving at least a portion of the messages (e.g., a copy of the entire message, email addresses and names of contacts of messages, etc.) for analysis (e.g., at server 102 from server 104, gateway 110, or server 106 of FIG. 1 ).

At 204, trusted contacts for a group that the user belongs to are determined. For example, trusted contacts for the users included in the group are aggregated to identify patterns among the aggregated trusted contacts. Examples of the group include a network domain that the user belongs to (e.g., domain of the email address of the user), an entity/organization that the user belongs to (e.g., company that the user belongs to), a message service provider, or an authority that controls a message account of the user. In some embodiments, determining trusted contacts for the group includes aggregating information about a trusted contact and/or a network domain of one or more trusted contacts from information gathered for different users for the trusted contact and/or the network domain. In some embodiments, determining the trusted contacts for the group includes storing information about the trusted contacts in a data storage structure and associating this stored information with the group.

At 206, determined trusted contacts are utilized to identify potential message threats for the user. For example, the contacts in the trusted contacts may be utilized as a proxy for contacts that are familiar to the user and if an attacker tries to attack the user using an impersonation attack, contact being impersonated likely corresponds to one of the contacts in the list of trusted contacts of the user. By determining a measure of similarity between a sender identifier of a message received for the user with each identifier of each trusted contact, messages attempting impersonation attacks may be identified. For example, if the email address of the sender matches an email address of a trusted contact, the message is to be trusted and not filtered but if the email address of the sender does not match any trusted contacts but is similar to an email address of a trusted contact, the message is identified as potentially a part of an impersonation attack and filtered. Filtering the message may include blocking the message, quarantining the message, further analyzing the message, and/or modifying the message (e.g., insert a warning).

FIG. 3 is a flowchart illustrating an embodiment of a process for determining information about a message sender to be utilized to assess a risk of a message. The process of FIG. 3 may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 . In some embodiments, at least a portion of the process of FIG. 3 is performed in 202 and/or 204 of FIG. 2 . For example, the process of FIG. 3 may be repeated for each trusted contact determined for a user (e.g., for each contact in a list of trusted contacts stored in a repository) and stored in a data structure that tracks the trusted contacts. The process of FIG. 3 may be repeated periodically.

At 302, a measure of global reputation for a sender is determined. The sender may correspond to a group of individual sender addresses in some embodiments or an individual sender address in other embodiments. For example, the sender corresponds to a trusted contact in a list of trusted contacts determined using the process of FIG. 2 . In another example, the sender corresponds to a domain of a trusted contact identified using the process of FIG. 2 . In some embodiments, the sender is a network/Internet domain and the measure of global reputation corresponds to all individual sender addresses of the domain. For example, the determined measure of global reputation of a domain is applicable to all email addresses within the domain. In some embodiments, the measure of global reputation for a sender is specific to an individual sender address. For example, the measure of global reputation for a sender is specific to an email address. In some embodiments, the sender is one of a plurality of senders in a list of senders to be analyzed to predetermine its global reputation. The list of senders may be automatically determined from one or more previously received messages (e.g., senders of previously received messages) and/or specified by a user/administrator. The measure of global reputation of the sender is applicable for a plurality of recipients of a message from the sender while a measure of local reputation of the sender is specific to a particular recipient domain or individual recipient address of a message from the sender.

In some embodiments, the measure of global reputation indicates a general measure that a sender is likely to send a message that is of value to a recipient of the message. For example, a higher measure of reputation indicates a higher likelihood that any message sent by the sender will not include malicious and/or undesired content (e.g., message will not include a virus, malware, spam, etc.). In some embodiments, determining the measure of global reputation includes determining one or more component factors to be utilized to determine a total measure of global reputation. For example, each determined component factor may be utilized to add, subtract, or multiply a value to/from the measure of global reputation to determine the total measure of global reputation. In one example, determined component factor values are summed to determine the global reputation measure. In some embodiments, machine learning or another automated process is utilized to determine the measure of global reputation based on gathered/generated information about the sender of the global reputation.

In some embodiments, determining the measure of global reputation for the sender includes determining whether an identifier of the sender (e.g., domain name, subdomain, IP address) is included in a list of senders known to be reputable. For example, there exists a predetermined list of entities and their associated identifiers that are known to be reputable and if the identifier of the sender is included in the predetermined list, the resulting measure of global reputation would be higher than otherwise. In some embodiments, determining the measure of global reputation for the sender includes determining whether an identifier of the sender is included in a list of senders known to be not reputable. For example, there exists a list of IP addresses associated with a server that are known to be commonly utilized to send spam messages and in the event an IP address associated with the sender is included in this list, the determined measure of global reputation would be lower than otherwise. Whether the identifier of the sender is included in the list of senders known to be reputable or not reputable may be utilized to determine a component factor value utilized in determining the measure of global reputation of the sender.

In some embodiments, determining the measure of global reputation for the sender includes determining a category of business associated with an entity of the sender. For example, businesses in certain categories (e.g., banking) may be associated with a higher reputation than businesses in other categories (e.g., digital marketing). In some embodiments, using a list/database that maps an identifier of a sender to a known associated category/line of business, the category/line of business associated with the sender is determined, if applicable (e.g., the line of business for some senders may be unknown or not applicable). A reputation component factor (e.g., value to be added, multiplied, or subtracted to/from total score measure) associated with the identified category/line of business may be utilized in determining the measure of global reputation.

In some embodiments, determining the measure of global reputation for the sender includes analyzing domain registration history and Domain Name System (i.e., DNS) activity of the sender. For example, a sender that is typically reputable will register a domain name far ahead of time prior to the use of the domain while a less reputable sender will likely temporarily utilize a domain for a short period of time prior to moving on to another domain and will register a domain within a short amount of time prior to the use of the domain. In some embodiments, determining the measure of global reputation includes utilizing a component factor value determined based on the domain registration history and DNS activity analysis (e.g., add, multiply, subtract, etc. using the factor value). For example, the factor value is based at least in part on a length of time since registration of a domain of the sender, an amount of time between registration of the domain and a first use of the domain to send a message, Internet content (e.g., webpage) located at a URI utilizing the domain of the sender, an entity that registered the domain of the sender, etc.

In some embodiments, determining the measure of global reputation for the sender includes analyzing historical statistics and/or a history of messages sent by the sender. For example, there exists one or more repositories of previous messages sent by the sender and the repositories of messages are analyzed to determine one or more of the following: an amount/volume/rate of messages sent by the sender, a number/breadth of different recipients (e.g., number of different domains of recipients, number of different email addresses of recipients, etc.) of messages from the sender, a distribution of messages sent to different recipients, a length of time the sender has been sending messages, a regularity that the sender has been sending messages (e.g., difference in average number of messages per time period), a type of content of messages sent by the sender, a difference/regularity between content of messages sent by the sender, amount/rate of content opened/viewed by recipients of messages sent by the sender, a number/rate of messages sent by the sender that have been identified as malware, spam, and/or a virus by an analysis/filter/scanner tool, etc. The historical analysis may be performed using machine learning. In some embodiments, based on the historical analysis, a historical analysis component factor value is determined and the historical analysis component factor value is added, multiplied, subtracted, etc. to determine the measure of global reputation for the sender.

In some embodiments, determining the measure of global reputation for the sender includes determining whether an identifier of the sender is similar to an identifier of another sender. For example, it is determined whether a domain of the sender is similar to a domain of another sender. Determining whether an identifier of the sender is similar to an identifier of another sender may include determining whether an identifier of the sender is similar to an identifier of another sender with a relatively high measure of global reputation. For example, an attempt to confuse a recipient by utilizing a domain that is only slightly different from a highly reputable domain is detected. In some embodiments, based on the similarity analysis, a similarity component factor value is determined and the similarity component factor value is added, multiplied, subtracted, etc. to determine the measure of global reputation for the sender.

In some embodiments, the global reputation for the sender is determined by combining (e.g., averaging, adding, etc.) measures of local reputation (determined in 304) for the sender determined for each recipient of a group of different recipients to determine a combined measure (e.g., combined score).

At 304, a specific measure of local reputation for the sender is determined for each of one or more different recipients. For example, although the measure of global reputation determined in 302 may apply to any recipient that receives a message from the sender, the specific measure of local reputation is only applicable to a specific recipient. In one example, one recipient may have a different relationship to a sender than another recipient (e.g., existing business relationship) and interest/relevance of a message from the sender may be different for different recipients and this difference is reflected as a different measure of local reputation for each different recipient. In some embodiments, the one or more different recipients include the user in 202 of the process of FIG. 2 . In some embodiments, the recipient represents a network/Internet domain and the measure of local reputation corresponds to all individual recipients of the domain. For example, the determined measure of local reputation for a recipient domain is applicable to all recipient email addresses within the domain. In some embodiments, the measure of local reputation for the sender is specific to an individual recipient address.

In some embodiments, the recipient is one of a plurality of recipients in a list of recipients to be analyzed to predetermine the local reputation of the sender for the specific recipient. The list of recipients may correspond to the recipients/email servers accessible (e.g., list of email domains being managed) by an analysis server. In some embodiments, each email server of each recipient performs its own determination of its measure of local reputation for the sender. In some embodiments, the measure of local reputation is determined dynamically. For example, when a recipient receives a message from the sender, the recipient determines the measure of local reputation for the sender.

In some embodiments, the measure of local reputation indicates a measure that the sender is likely to send a message that is of value to a specific recipient. For example, a higher measure of reputation indicates a higher likelihood that an authentic message sent by the sender will not include malicious and/or undesired content (e.g., message will not include a virus, malware, spam, etc.) for the specific recipient. In some embodiments, determining the measure of local reputation includes determining one or more factors to be utilized to determine a total measure of local reputation. For example, each determined factor may be utilized to add, subtract, or multiply a value to/from the measure of local reputation to determine the total measure of local reputation. In some embodiments, machine learning or another automated process is utilized to determine the measure of local reputation based on gathered/generated information about the sender.

In some embodiments, determining the measure of local reputation for the sender includes determining whether an identifier of the sender (e.g., domain name, subdomain, IP address) is included in a list of senders known to be reputable for the recipient. For example, there exists a predetermined list of entities and their associated identifiers that are known to be reputable for the specific recipient. If the identifier of the sender is included in the predetermined list, the resulting measure of local reputation would be higher than otherwise. In some embodiments, determining the measure of local reputation for the sender includes determining whether an identifier of the sender is included in a list of senders known to be not reputable for the specific recipient. For example, there exists a list of IP addresses associated with a server that are known to be commonly utilized to send spam messages and in the event an IP address associated with the sender is included in this list, the determined measure of local reputation would be lower than otherwise. Whether the identifier of the sender is included in the list of senders known to be reputable or not reputable may be utilized to determine a component factor value utilized to determine the measure of local reputation of the sender.

In some embodiments, determining the measure of local reputation for the sender includes determining a category of business associated with an entity of the sender with respect to a property of the specific recipient. For example, businesses in certain categories (e.g., banking) may be associated with a higher reputation than businesses in other categories (e.g., digital marketing) with respect to the category of business of the recipient (e.g., recipient is also in banking). In some embodiments, a reputation component factor (e.g., value to be added, multiplied, or subtracted to/from total score measure) associated with the identified category/line of business with respect to the recipient may be utilized in determining the measure of local reputation

In some embodiments, determining the measure of local reputation for the sender includes analyzing domain registration history and Domain Name Service (i.e., DNS) activity of the sender with respect to a property of the recipient. For example, it may be typical for certain recipients to be in communication with senders that utilize a domain for a short period of time while for other recipients it is not typical. In some embodiments, determining the measure of local reputation includes utilizing a component factor value determined based on the domain registration history and DNS activity analysis (e.g., add, multiply, subtract, etc. using the factor value). For example, the factor value is based at least in part on a length of time since registration of a domain of the sender, an amount of time between registration of the domain and a first use of the domain to send a message, Internet content (e.g., webpage) located at a URI utilizing the domain of the sender, an entity that registered the domain of the sender, etc.

In some embodiments, determining the measure of local reputation for the sender includes analyzing historical statistics and/or a history of messages sent by the sender for the specific recipient domain or individual recipient addresses. For example, there exists a repository of previous messages sent by the sender to the recipient (e.g., messages stored at a recipient message server of the recipient) and the repository of messages is analyzed to determine one or more of the following: an amount/volume/rate of messages sent by the sender, a number/breadth of different individual users of the recipient (e.g., number of different email addresses of recipient) that received messages from the sender, a distribution of messages sent to different individual users of the recipient, a length of time the sender has been sending messages to the recipient, a regularity that the sender has been sending messages to the recipient (e.g., difference in average number of messages per time period), a type of content of messages sent by the sender to the recipient, a difference/regularity between content of messages sent by the sender to the recipient, amount/rate of content opened/viewed by the recipient of messages sent by the sender, a number/rate of messages sent by the sender that have been identified as malware, spam, and/or a virus by an analysis/filter/scanner tool, etc. The historical analysis may be performed using machine learning. In some embodiments, based on the historical analysis, a historical analysis component factor value is determined and the historical analysis component factor value is added, multiplied, subtracted, etc. to determine the measure of local reputation of the sender for the recipient.

In some embodiments, determining the measure of local reputation for the sender includes determining whether an identifier of the sender is similar to an identifier of another sender and/or an identifier of the recipient. For example, it is determined whether a domain of the sender is similar to a domain of another sender or a domain of the recipient. Determining whether an identifier of the sender is similar to an identifier of another sender or the recipient may include determining whether an identifier of the sender is similar to an identifier of another sender with a relatively high measure of local reputation for the recipient. For example, an attempt to confuse a user by utilizing a sender domain that is only slightly different from a highly reputable domain for the recipient is detected. In some embodiments, an attempt to confuse a user by utilizing a sender domain that is only slightly different from a domain of the recipient is detected (e.g., detect trying to mimic an intra-organization message). In some embodiments, based on the similarity analysis, a similarity component factor value is determined and the similarity component factor value is added, multiplied, subtracted, etc. to determine the measure of local reputation of the sender for the recipient.

At 306, a global sender model for the sender is determined. For example, the sender model may be utilized to determine whether a message that indicates a sender was actually sent by the indicated sender. In some embodiments, the sender model identifies one or more properties that are characteristic of a message that is sent by the sender. In some embodiments, the sender model associates the sender with one or more IP addresses of message servers that are known or authorized to send messages for the sender. For example, an IP address of a last server that sent a message is a reliable identifier that indicates an origin of the message and this IP address information is utilized to determine whether the last server that sent the message corresponds to the sender identified in the message. In some embodiments, the sender model includes directly provided information. For example, a list of IP addresses of servers that send messages for the sender is received from a user, the sender, or a published source of information about the sender. In some embodiments, at least a portion of the sender model is determined using message authentication/validation information about the sender. For example, IP addresses associated with a domain of the sender are obtained using standardized message authentication/validation systems (e.g., using Domain-based Message Authentication (DMARC), DomainKeys Identified Mail (DKIM), Sender Policy Framework (SPF), etc.).

In some embodiments, the sender model is automatically determined. For example, using one or more repositories storing messages received from the sender, a list of server IP addresses authorized or historically known to send messages for the sender is automatically determined. The one or more repositories may include a message store of a plurality of different recipients (e.g., different recipient message servers managed by an analysis server) and external message sources (e.g., information from third-party sources that gather message information). Machine learning may be utilized to automatically detect sources of and properties that are characteristic of authentic messages from the sender using historical information about messages previously sent by or on behalf of the sender. In some embodiments, an IP address is automatically associated with the sender in the sender model if it is detected that a message likely/verified to be sent by the sender was sent from the IP address. In some embodiments, before an IP address is associated with the sender, the sender must have sent a message from the IP address at least a threshold number of times. In some embodiments, a message is determined to have been sent by the sender if the message was validated using an email authentication/validation system and/or sent from the IP address that has been utilized to send messages identified as being sent by the sender for at least a threshold amount of time and/or a threshold number of times. Other factors may be utilized to verify whether a message in a repository was sent by the sender prior to using IP address information of the message in determining the sender model of the sender.

In some embodiments, an IP address is only added to the sender model to be associated with the sender in the event the IP address has been determined to be consistent for the sender. For example, a history of senders associated with the IP address is analyzed and the IP address is only associated with the sender if the IP address is not already associated with another sender, has not been associated with another sender for at least a threshold amount of time, and/or the number of different previous senders that have been with associated with the IP address is less than a threshold number.

In some embodiments, the sender model identifies one or more blocks of adjacent IP addresses that are authorized or historically known to send messages on behalf of the sender. These blocks of adjacent IP addresses may be owned or be under the control of a single administrative entity or domain or may be detected to exhibit similar sending behavior. The block of adjacent IP addresses may be specified by a user, a sender, an administrator, and/or a source of published information about the sender or a provider authorized by the sender. In some embodiments, one or more blocks of adjacent IP addresses to be included in the sender model are automatically determined. For example, once one or more IP addresses within a block of adjacent IP addresses have been associated with a sender model, the entire block of adjacent IP addresses may be associated with the sender model if they are determined or expected to exhibit similar message sending behavior.

In some embodiments, the sender model identifies a network/Internet domain that is common to all hostnames of servers that are authorized or historically known to send messages on behalf of the sender. The servers that share this network/Internet domain may be owned or be under the control of a single administrative entity or domain or may be detected to exhibit similar sending behavior. The network/Internet domain may be specified by a user, a sender, an administrator, and/or a source of published information about the sender or a provider authorized by the sender. In some embodiments, the network/Internet domain to include within the sender model is automatically determined. For example, once one or more IP addresses whose hostnames share an organizational network/Internet domain have been associated with a sender model, all servers whose hostnames share that network/Internet domain may be associated with the sender model if they are determined or expected to exhibit similar message sending behavior.

In some embodiments, the sender model identifies one or more autonomous system numbers (i.e., ASN) associated with servers that are authorized or historically known to send messages on behalf of the sender. For example, an ASN identifies a collection of IP routing prefixes owned by or under the control of a single administrative entity or domain and the ASN associated with the sender is specified in the sender model. The ASN associated with the sender may be specified by a user, a sender, an administrator, and/or a source of published information about the sender. In some embodiments, the ASN associated with the sender is automatically determined. For example, once one or more IP addresses associated with a sender model have been identified, the ASN(s) associated with the IP addresses may be associated with the sender if they are determined or expected to exhibit similar message sending behavior.

The determined or specified sender model associated with a sender may be stored in a data structure such as a list, a database, a table, or any other data structure that can be indexed based on an identifier of the sender.

At 308, a specific sender model for the sender is determined for each of one or more recipients, if applicable. For example, although the sender model determined in 306 may apply to any recipient, the specific sender model is only applicable to a specific recipient. In one example, one recipient may receive a message from the sender via a different set of sending message servers than another recipient due to geographical location differences between the recipients. In some embodiments, the recipient represents a network/Internet domain and the recipient specific sender model corresponds to all individual recipients of the domain. In some embodiments, the recipient specific sender model is specific to an individual recipient address. In some embodiments, the recipient specific sender model is determined in a similar manner as the sender model determined in 306 except for utilizing data specific to the recipient rather than various different recipients. For example, using a repository storing messages received from the sender to only the recipient, individual or neighborhoods of IP addresses associated with the sender model for a sender are automatically determined.

FIG. 4 is a flowchart illustrating an embodiment of a process for determining a total risk measure of a contact. The process of FIG. 4 may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 .

At 402, a measure of trust associated with a message contact is determined. In some embodiments, the measure of trust (e.g., numerical value) indicates a measure that the message contact is likely to send a message that is of value to a recipient/user. For example, a higher measure of trust indicates a higher likelihood that an authentic message sent by the contact will not include malicious and/or undesired content (e.g., message will not include a virus, malware, spam, impersonation attack, etc.). The measure of trust may be for a domain of the message contact that covers all messages of the same domain, a group of domains (e.g., domains of similar category), a group of contact addresses, or a specific contact address (e.g., email address). In some embodiments, the measure of trust is for a specific recipient/user. For example, the measure of trust indicates a measure of trust between the message contact and a specific recipient/user. In this example, the measure of trust may be determined based on a history of interaction between the message contact and the specific user.

In some embodiments, the measure of trust is determined at least by a portion of the process of FIG. 3 . For example, the measure of trust is the specific measure of local reputation determined in 304. In another example, the measure of trust is the measure of global reputation included in the global sender model determined in 306. In another example, the measure of trust is determined based on a combination (e.g., average, sum, product, etc.) of the measure of global reputation and the specific measure of local reputation.

At 404, a measure of spoofing risk associated with the message contact is determined. For example, a likelihood that a spoofing attack could be technically carried out to spoof the message contact is determined. The measure of spoofing risk may be for a domain of the message contact that covers all messages of the same domain, a group of domains, a group of contact addresses, or a specific contact address (e.g., email address). The measure of spoofing risk may be a numeric score corresponding to the spoofing risk associated with the message contact.

An organization with a published and complete Domain-based Message Authentication, Reporting and Conformance (i.e., DMARC) policy has a low risk of being spoofed, as does each user account associated with such an organization. An organization that has a DMARC policy but which does not reject all messages that fail corresponds to a medium risk, as do users of such an organization. An organization without a DMARC policy or one that only involves monitoring and no rejection is associated with a high risk of being spoofed, as are users of such an organization. For example, if the message contact is associated with a DMARC policy that requires every message of the domain of the message contact to be signed with a digital signature, the measure of spoofing risk is assigned a low risk value. If the message contact is associated with a DMARC policy that enables but does not require every message of the domain of the message contact to be signed with a digital signature, the measure of spoofing risk is assigned a medium risk value. If the message contact is not associated with a DMARC policy, the measure of spoofing risk is assigned a high risk value. Thus, determining the measure of spoofing risk associated with the message contact may include assigning a score based on the DMARC or other message validation system policy associated with the message contact.

At 406, the measure of trust and the measure of spoofing risk are combined to determine a measure of total risk associated with the message contact. For example, the measure of trust and the measure of spoofing risk are multiplied together to determine the measure of total risk. In another example, the measure of trust and the measure of spoofing risk are averaged together to determine the measure of total risk. In another example, the measure of trust and the measure of spoofing risk are summed together to determine the measure of total risk. Thus, the measure of total risk is able to measure the threat of the message contact being impersonated, both in terms of the likely impact to the recipient (e.g., measure of trust provides a gauge on the likelihood the message recipient is likely to confuse the spoofed message as a message from a highly trusted and important contact) and the likelihood of technical feasibility (e.g., measure of spoofing risk provides a gauge on the measure of technical feasibility). In some embodiments, the measure of trust and the measure of spoofing risk may be each weighted before being combined. In some embodiments, the determined measure of total risk is stored in a data structure and associated with the message contact.

At 408, the measure of total risk is utilized to mitigate risk of messages received from the message contact. For example, when a message from the message contact is received, its measure of total risk for the sender of the message (e.g., message contact) is obtained and the measure of total risk is utilized to determine whether to filter and/or allow the message to be delivered. In an example, if a value of the measure of total risk is above a threshold value, the message is identified as a risk and the message is filtered to reduce its risk to the recipient.

FIG. 5 is a flowchart illustrating an embodiment of a process for assessing a received message for filtering. The process of FIG. 5 may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 .

At 502, information about a message is received. In some embodiments, the information is received at analysis server 102 of FIG. 1 . The information may include information about a sender of the message. For example, the information includes email address header information including an email address and a display name of the sender of the message. In some embodiments, the information about the message includes contents of the message. Examples of the message include an electronic mail (i.e., email), an instant message, a chat message, and any other forms of electronic messages.

At 504, it is determined whether a sender of the message exactly matches a trusted contact. For example, it is determined whether an address of the sender of the message (e.g., in a “From:” field of a message header) exactly matches an address of a trusted contact in a list of trusted contacts for the recipient of the message. In some embodiments, the trusted contacts include trusted contacts identified in 202 and/or 204 of FIG. 2 . For example, a list of trusted contacts for the recipient of the message is obtained from storage and email addresses for each trusted contact of the list are compared with the email address of a sender of the message to identify whether there is an exact match.

If at 504 it is determined that the sender of the message exactly matches the trusted contact, at 506, the message is allowed to be fully accessed by the recipient, if applicable. For example, because the sender of the message exactly matches the trusted contact, the message is allowed to be delivered (e.g., by sending the message to a mail delivery server and indicating that the message is allowed to be delivered) to the recipient user. In some embodiments, the message is allowed to be accessed by the recipient without message filtering that would otherwise be performed if the message was identified as potentially a part of an impersonation attack. In some embodiments, the message is further analyzed prior to allowing it to be fully accessed by the recipient. For example, the message may be analyzed to identify whether it includes a virus, a spam, or a malware. In some embodiments, the total risk score determined using 406 of FIG. 4 is utilized to determine whether to allow full access to the message. If a value of the measure of total risk of the sender is above a threshold value, the message is identified as a risk and the message is filtered as in 510 to reduce its risk to the recipient.

If at 504 it is determined that the sender of the message does not exactly match a trusted contact, at 508, it is determined whether the sender of the message is similar to a trusted contact. For example, by determining whether the sender of the message is similar to a trusted contact, a likelihood of confusion by a recipient of the message that the message is from a trusted contact is determined. In some embodiments, the determining whether the sender of the message is similar to a trusted contact includes determining a measure of similarity between the sender of the message and each contact in a list of trusted contacts. In some embodiments, the list of trusted contacts includes trusted contacts identified in 202 and/or 204 of FIG. 2 . For example, a list of trusted contacts for the recipient of the message (e.g., recipient identified in a “To:” field of the message) is obtained from storage.

In some embodiments, determining the measure of similarity includes determining a string similarity measure (e.g., string distance) using a string matching algorithm (e.g., Jaro-Winkler). For each trusted contact in a group of trusted contacts, string similarity measures may be determined between an address of the trusted contact and/or a display name of the trusted contact with an address of the sender of the message (e.g., string in a “From:” field of the message between “<” and “>” characters), a display name of the sender of the message (e.g., string in a “From:” field of the message prior to “<” character), and/or a subject of the message. For example, potentially six string similarity measures may be determined for each trusted contact email/display name combination (e.g., trusted contact address compared to sender address, trusted contact address compared to sender display name, trusted contact address compared to message subject, trusted contact display name compared to sender address, trusted contact display name compared to sender display name, and trusted contact display name compared to message subject).

Comparison of the subject to the message to the trusted contact address/display name is performed to detect masquerade attempts in which the actual sender uses deceptive display names and/or subject lines to trick recipients that emails are from a trusted sender. For example, the sender joe123@gmail.com may set his display name to appear as a subject line, and use a subject line that appears as a from email address. This attacker may use the display name “Please review this material and let me know your thoughts. Fwd: slide deck, June 15 version,” and the subject line “Bob Bigboss <bbigboss@bigbossventures.com>” to an email. The display name, being very long, will often hide the attacker's email address (e.g., which is displayed after the display name for a typical mail client, or not displayed at all for some mail clients). Many recipients will not realize that the subject line appears where the sender address is normally shown, and vice versa. Therefore, such recipients will believe that the email comes from Bob Bigboss <bbigboss@bigbossventures.com>, despite it being displayed in the subject field. In some embodiments, the subject of the message is only utilized to perform the determination of the measure of similarity if the display name of the sender of the email is longer than a threshold length.

In some embodiments, prior to performing the string comparison to determine the measure of similarity, element portions of the strings are sorted (e.g., alphabetically sorted) based on a predetermined order. The element portions of the string may be delimited by a space character or other special characters (e.g., comma, period, etc.). For example, strings “Bob Bigboss” and “Bigboss Bob” may be determined to be not similar in string distance despite them being a simple reversal of the order of the first/last names. Thus, the element portions “Bob” “Bigboss” in “Bob Bigboss” can be alphabetically sorted as “Bigboss Bob” prior to being used in the string comparison.

In some embodiments, determining the measure of similarity includes detecting use of substitution characters that mimic corresponding traditional alphabet/number characters in the sender address, sender display name, and/or subject of the message prior to comparison with identifiers of the trusted contact. For example, an attacker may use substitution characters to visually mimic a character in an identifier of a trusted contact (e.g., replace “o” with zero, replace with Cyrillic letter, replace with Greek letter, replace with symbol resembling a traditional letter/number, etc.). In some embodiments, if substitution characters are detected, various versions of the sender address, sender display name, and/or subject of the message that replace one or more different combinations of substitution characters with corresponding traditional characters are generated and utilized in the string comparisons with the identifiers of the trusted contacts.

In some embodiments, it is determined that the sender of the message is similar to a trusted contact if any measure of similarity (e.g., string distance measure) meets a threshold value. For example, if any string distance measure determined for a list of trusted contacts is greater than a threshold value, the message is identified as potentially an impersonation attack message and it is determined that the sender of the message is similar to the trusted contact.

In some embodiments, messages that are highly authentic (e.g., associated with a valid DMARC signature, correct SPF records, or both) but which come from domains that are associated with low control are to be subject to increased analysis. For example, a measure of control of the domain of the sender is determined. The measure of control measures how easy it is to create an account of the domain without having to pass a careful screening. For example, any user is able to create a Google Gmail account by setting the username to any available user name and setting the display name to any correctly formed display name. Thus, domains correspond to a very low degree of control by the domain owner. In contrast, the typical enterprise or government entity has high control over account creation, allowing only employees and affiliates to create accounts, where these have to satisfy some common criteria related to the real-life identity of the user. When the message is identified as having high authenticity but low domain control, then the display name is to be scrutinized (e.g., compared to trusted display names using string distance as previously discussed), whereas for domains with high control, the display name is not scrutinized (e.g., display name impersonation detection not performed).

If at 508 it is determined that the sender of the message is similar to a trusted contact, at 510, the message is filtered, if applicable. Filtering the message may include modifying at least a portion of the message, affecting delivery of the message, providing a notification regarding the message, and/or performing additional analysis on the message. An example of filtering the message is performing a security action.

In some embodiments, modifying at least a portion of the message includes modifying (e.g., replacing, adding or removing/deleting) data included in a data field (of the message) that includes an identification of the sender of the message. For example, the data field that is identified to include the identification of the sender is selected from a plurality of data fields of a message header and contents of the selected data field is modified. Examples of the identification of the sender includes a display name, an email address (e.g., “from” email address), a reply-to address, a phone number, an image, a content link, or any other identifier/identification of the sender specified in the message. The data field of the message may be included in a header of the message. For example, the data field of the message is a “From:” field, a “Reply-To:” field or a “Return-Path:” field of an email message header. In some embodiments, the message is a SMS message or a MMS message and a phone number of the sender in the data field is modified. For example, the sender phone number is removed or changed to a different number. In some embodiments, modifying data included in the data field includes modifying a location identifier of content associated with the sender of the message. For example, a URL to an image of the sender is modified to reference a different image (e.g., replacement image includes a warning message).

One example filtering is quarantining the message and sending an automated message to the email address in the “From:” field of the message regarding the quarantine. The automated email may require the recipient to click on a hyperlink that is unique and not predictable to an attacker. If the system determines that such a link was clicked on (e.g., by receiving a corresponding GET request), then the email may be taken out of quarantine and delivered.

Another example filtering is sending an automated email in response to the received message (e.g., whether to the address in the from field or a potential address in the ‘reply-to’ field or both), requiring the recipient to click on a hyperlink where he or she has to enter a code obtained from an authenticator module, such as a SecurID token or Google authenticator app. If the entered code is correct, the message is taken out of quarantine and delivered.

In an alternative embodiment, the received message is not quarantined but delivered to its recipient after being modified. For example, a warning message is added to one or more header fields and/or the body of the message (e.g., add warning message to subject of message, add warning message to modify sender address, etc.). In some embodiments, the received message is modified to change, remove, and/or censure at least a portion of the message (e.g., remove attachment, remove hyperlinks, remove/modify reply to address, etc.).

If at 508 it is determined that the sender of the message is not similar to a trusted contact, the process returns to 506. In an alternative embodiment, if at 508, it is determined that the sender of the message is not similar to a trusted contact, the message identified for filtering if the recipient of the message has never sent a message to the sender of the message. In some embodiments, the total risk score determined using 406 of FIG. 4 is utilized to determine whether to allow full access to the message. If a value of the measure of total risk of the sender is above a threshold value, the message is identified as a risk and the message is filtered in 510 to reduce its risk to the recipient.

FIG. 6A is a flowchart illustrating an embodiment of a process for modifying a display name of a sender of the message. The process of FIG. 6A may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 . In some embodiments, at least a portion of the process of FIG. 6A is performed in filtering the message in 506 and/or 510 of FIG. 5 .

At 602, a message is identified as suspicious. For example, it is identified in 508 that a sender of the message is similar to a trusted contact based on a measure of similarity of a sender of the contact with a trusted contact of a particular identified recipient of the message. An example of a trusted contact is a contact that has been previously identified by the recipient (e.g., included in an address book of the recipient) or is a contact with whom the recipient has had at least a minimum amount of positive engagement (e.g., having exchanged emails at least twice, and at least two weeks apart) without a recent “negative engagement” (e.g., recipient has not recently marked a message from the contact as spam). In some embodiments, the message is identified as suspicious if a sender of the message has not previously sent a message to a recipient identified in the message. In some embodiments, the message is identified as suspicious if a recipient identified in the message has not previously sent a message to the sender of the message. In some embodiments, the message is identified as suspicious if a spam detector, a virus detector, and/or a malware detector has detected that the message includes a spam, virus or malware.

At 604, a display name of a sender of the message is modified prior to allowing the message to be accessed by a recipient user of the message. For example, the display name of the sender is rewritten to include a warning regarding its risk. In one example, consider an email with display name “Pat Peterson,” but not associated with an email address of a Pat Peterson that is considered trusted. This may cause the system to determine that the email is risky, and modify the display name to “Warning! Unknown user with the name ‘Pat Peterson.’” Conversely, if an email is determined to come from a trusted sender, the system may modify the display name by adding symbol(s) (e.g., icon of a star) identifying its risk. In some embodiments, display names of senders in messages identified as not suspicious are normalized, which may involve removing anything looking like a trust indicator (e.g., such as an icon of a star) from the display name, or adding another symbol to the display name. Alternatively, a message from a user that is neither considered risky nor trusted could have its display name removed and replaced by only the message address of the sender (e.g., only email address without display name), drawing the attention of the recipient to the fact that this is a user with whom the system has not determined there to be a trust relationship. This may be particularly beneficial to users who use mail clients that do not display the full email address, but only show the display name.

In some embodiments, in addition to or instead of the display name, an email address of the sender is also modified. For example, the entire “From:” field of a header of the message that includes both the display name and an email address is modified with a warning.

FIG. 6B is a flowchart illustrating an embodiment of a process for modifying a reply address of a sender of the message. The process of FIG. 6B may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 . In some embodiments, at least a portion of the process of FIG. 6B is performed in filtering the message in 506 and/or 510 of FIG. 5 .

At 612, a message is identified as suspicious. For example, it is identified in 508 that a sender of the message is similar to a trusted contact based on a measure of similarity of a sender of the contact with a trusted contact of a particular identified recipient of the message. An example of a trusted contact is a contact that has been previously identified by the recipient (e.g., included in an address book of the recipient) or is a contact with whom the recipient has had at least a minimum amount of positive engagement (e.g., having exchanged emails at least twice, and at least two weeks apart) without a recent “negative engagement” (e.g., recipient has not recently marked a message from the contact as spam). In some embodiments, the message is identified as suspicious if a sender of the message has not previously sent a message to a recipient identified in the message. In some embodiments, the message is identified as suspicious if a recipient identified in the message has not previously sent a message to the sender of the message. In some embodiments, the message is identified as suspicious if a spam detector, a virus detector, and/or a malware detector has detected that the message includes a spam, virus or malware.

At 614, a reply address of a sender of the message is modified prior to allowing the message to be accessed by a recipient user of the message. In the event where the message does not have a reply address, a “Reply-To:” field is automatically added to the message. This can be a real email address, different from the “from” address of the received message, and act as a quarantine for outgoing responses to high-risk emails. In such a quarantine, the recipient system can carefully verify (e.g., whether automatically or using manual effort, or a combination thereof) that the outgoing message is safe before it is automatically sent to the “from” address of the received email.

In some embodiments, an address in a “Reply-To:” field of an email header is replaced or inserted with a warning message (e.g., not a valid reply address) regarding the suspicious risk of the message. In one example, the “reply to” address of a message is replaced/created as “Warning! This is a user you have never sent an email to—If you want to proceed, remove this text from the recipient field of the email you want to send, and add the address of the recipient you wish to send it to.” This reply address will cause a pop-up on some message clients with the text above (e.g., and an error stating that it is not a valid email address) or may cause on some message clients to bounce the email.

FIG. 7 is a flowchart illustrating an embodiment of a process for securing a message. The process of FIG. 7 may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 . In some embodiments, at least a portion of the process of FIG. 7 is performed in filtering the message in 506 and/or 510 of FIG. 5 . In some embodiments, at least a portion of the process of FIG. 5 is performed in the process of FIG. 7 .

At 702, a first risk analysis of the message is performed. For example, it is determined whether the message is suspicious. In some embodiments, steps 504 and/or 506 of FIG. 5 is performed in 702. For example, it is determined whether the sender of the message is similar to a trusted contact. By determining whether the sender of the message is similar to a trusted contact, a likelihood of confusion by a recipient of the message that the message is from a trusted contact may be determined. In some embodiments, the determining whether the sender of the message is similar to a trusted contact includes determining a measure of similarity between the sender of the message and each contact in a list of trusted contacts. In some embodiments, the list of trusted contacts includes trusted contacts identified in 202 and/or 204 of FIG. 2 . For example, a list of trusted contacts for the recipient of the message (e.g., recipient identified in a “To:” field of the message) is obtained from storage.

In some embodiments, determining the measure of similarity includes determining a string similarity measure (e.g., string distance) using a string matching algorithm (e.g., Jaro-Winkler). For each trusted contact in a group of trusted contacts, string similarity measures may be determined between an address of the trusted contact and/or a display name of the trusted contact with an address of the sender of the message (e.g., string in a “From:” field of the message between “<” and “>” characters), a display name of the sender of the message (e.g., string in a “From:” field of the message prior to “<” character), and/or a subject of the message. For example, potentially six string similarity measures may be determined for each trusted contact email/display name combination (e.g., trusted contact address compared to sender address, trusted contact address compared to sender display name, trusted contact address compared to message subject, trusted contact display name compared to sender address, trusted contact display name compared to sender display name, and trusted contact display name compared to message subject).

Comparison of the subject to the message to the trusted contact address/display name is performed to detect masquerade attempts in which the actual sender uses deceptive display names and/or subject lines to trick recipients that emails are from a trusted sender. For example, the sender joe123@gmail.com may set his display name to appear as a subject line, and use a subject line that appears as a from email address. This attacker may use the display name “Please review this material and let me know your thoughts. Fwd: slide deck, June 15 version,” and the subject line “Bob Bigboss <bbigboss@bigbossventures.com>” to an email. The display name, being very long, will often hide the attacker's email address (e.g., which is displayed after the display name for a typical mail client, or not displayed at all for some mail clients). Many recipients will not realize that the subject line appears where the sender address is normally shown, and vice versa. Therefore, such recipients will believe that the email comes from Bob Bigboss <bbigboss@bigbossventures.com>, despite it being displayed in the subject field. In some embodiments, the subject of the message is only utilized to perform the determination of the measure of similarity if the display name of the sender of the email is longer than a threshold length.

In some embodiments, prior to performing the string comparison to determine the measure of similarity, element portions of the strings are sorted (e.g., alphabetically sorted) based on a predetermined order. The element portions of the string may be delimited by a space character or other special characters (e.g., comma, period, etc.). For example, strings “Bob Bigboss” and “Bigboss Bob” may be determined to be not similar in string distance despite them being a simple reversal of the order of the first/last names. Thus, the element portions “Bob” “Bigboss” in “Bob Bigboss” can be alphabetically sorted as “Bigboss Bob” prior to being used in the string comparison.

In some embodiments, determining the measure of similarity includes detecting use of substitution characters that mimic corresponding traditional alphabet/number characters in the sender address, sender display name, and/or subject of the message prior to comparison with identifiers of the trusted contact. For example, an attacker may use substitution characters to visually mimic a character in an identifier of a trusted contact (e.g., replace “o” with zero, replace with Cyrillic letter, replace with Greek letter, replace with symbol resembling a traditional letter/number, etc.). In some embodiments, if substitution characters are detected, various versions of the sender address, sender display name, and/or subject of the message that replace one or more different combinations of substitution characters with corresponding traditional characters are generated and utilized in the string comparisons with the identifiers of the trusted contacts.

At 704, it is determined whether the first risk analysis results in a determination that the message meets a first criteria. For example, it is determined whether the message meets a criteria to be deemed suspicious. In some embodiments, message meets the first criteria if a measure of similarity (e.g., string distance measure) meets a threshold value. For example, if any string distance measure determined for a list of trusted contacts (e.g., determined in 702) is greater than a threshold value, the message is identified as potentially an impersonation attack message and it is determined that the message meets the first criteria.

In some embodiments, the message meets the first criteria if a sender of the message has not previously sent a message to a recipient identified in the message. In some embodiments, the message meets the first criteria if a recipient identified in the message has not previously sent a message to the sender of the message. In some embodiments, the message meets the first criteria if a spam detector, a virus detector, and/or a malware detector has detected that the message includes a spam, virus or malware.

In some embodiments, a total risk score determined using 406 of FIG. 4 is utilized to determine whether message meets the first criteria. For example, if a value of the measure of total risk of the sender is above a threshold value, the message is identified as meeting the first criteria.

If at 704 it is determined that the message does not meet the first criteria, at 706 the message is allowed to be fully accessed by the recipient, if applicable. For example, because the sender of the message exactly matches the trusted contact or sender of the message is not similar to any trusted contact, the message is allowed to be delivered (e.g., by sending the message to a mail delivery server and indicating that the message is allowed to be delivered) to the recipient user. In some embodiments, the message is allowed to be accessed by the recipient without message filtering that would otherwise be performed if the message was identified as potentially a part of an impersonation attack. In some embodiments, the message is further analyzed prior to allowing it to be fully accessed by the recipient. For example, the message may be analyzed to identify whether it includes a virus, a spam, or a malware.

If at 704 it is determined that the message does meet the first criteria, at 708 the message is modified prior to sending a modified version of the message to a specified recipient of the message. For example, a warning message is added to one or more header fields and/or the body of the message (e.g., add warning message to subject of message, add warning message to modify sender address, etc.). The first risk analysis is performed before sending the modified version of the message. Sending the modified version may include delivering the modified version to the specified recipient (e.g., deliver to a mailbox of the specified recipient on server 106 of FIG. 1 ).

In some embodiments, modifying at least a portion of the message includes modifying (e.g., replacing, adding or removing/deleting) data included in a data field of the message that includes an identification of the sender of the message (e.g., modify an identifier of the sender). Examples of the identification of the sender includes a display name, an email address (e.g., “from” email address), a reply-to address, or any other identifier/identification of the sender specified in the message. The data field of the message may be included a header of the message. For example, the data field that includes the identification of the sender is a “From:” field, a “Reply-To:” field or a “Return-Path:” field of an email message header. The contents of the data field may be modified to provide a warning to a recipient, prevent a potential confusion of an identity of the sender of the message by the recipient of the message and/or prevent the recipient from responding to the message or sending a message to the sender of the message.

In some embodiments, the received message is modified to change, remove, and/or censure at least a portion of a content of the message (e.g., remove attachment, remove hyperlinks, remove a portion of the message content beyond a selected beginning body portion, etc.). For example, a message body section of an email message is modified to censure at least a portion of a content of the email message. In some embodiments, modifying the message includes inserting an inquiry associated with a verification of the sender of the message, wherein the inquiry requests a user response.

At 710, a second risk analysis of the message is performed and it is determined whether the second risk analysis results in a determination that the message meets the second criteria. In some embodiments, the modified version of the message is sent to the specified recipient of the message (e.g., sent to a mailbox of the specified recipient on server 106 of FIG. 1 ) prior to a conclusion of the second risk analysis. For example, the modified version of the message is sent and delivered to a mailbox of the specified recipient of the message prior to the conclusion of the second risk analysis. In some embodiments, the second risk analysis concludes upon determination of whether the second risk analysis results in a determination that the message meets the second criteria.

In some embodiments in 710, any of a plurality different types of verification/security actions may be performed to further analyze and verify the message (e.g., verify an identity of the sender of the message). For example, it is determined whether a classification of the sender of the message requested and received from the specified recipient of the message matches an automatically identified classification of the sender, and it is determined the message meets the second criteria if a user response to the requested classification matches the automatically identified classification (e.g., see the process of FIG. 8A). In another example, an automatically generated reply message to a received message is sent the sender of the received message requesting verification of an identity of the sender of the message and it is determined the message meets the second criteria if the sender has provided a valid identity in response to the reply message (e.g., see the process of FIG. 9A).

If 710 it is determined that the second risk analysis results in a determination that the message meets the second criteria, at 712, content of the message that was previously prevented from being accessed by the specified recipient is provided to the specified recipient of the message. The second risk analysis may be a more in-depth and/or resource intensive analysis of the message reserved for messages that fail the first risk analysis. For example, an original version of the message prior to the modification in 708 is sent to the specified recipient of the message. This original version may be a duplicate message in addition to the initially provided modified version of the message (e.g., original version delivered as a new message to the specified recipient) or this original version may be a replacement message of the initially provided modified version of the message (e.g., initially provided modified message is deleted from mailbox of the specified recipient of the message and replaced with the original version). In some embodiments, the content of the message that was previously prevented from being accessed is included a new message sent to the specified recipient of the message.

If 710 it is determined that the second risk analysis results in a determination that the message does not meet the second criteria, at 714 content of the message that was prevented from being accessed by the specified recipient remains not accessible by the specified recipient. In some embodiments, the message is deleted or quarantined. For example, after a period of time of message not meeting the second criteria and/or if it is determined during the second risk analysis that the message is potentially hazardous to a specified recipient of the message, the message is automatically deleted or quarantined to prevent access by the specified recipient to the entire message. In some embodiments, a notification is provided to an administrator. For example, the administrator is provided a warning about the message failing the second risk analysis.

FIG. 8A is a flowchart illustrating an embodiment of a process for detecting misrecognition of a sender of a message by a recipient of the message. The process of FIG. 8A may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 . In some embodiments, at least a portion of the process of FIG. 8A is performed in filtering the message in 506 and/or 510 of FIG. 5 . In some embodiments, least a portion of the process of FIG. 8A is performed in one or more steps of the process of FIG. 7 . For example, at least a portion of the process of FIG. 8A is performed in performing the first and/or second risk analysis of the process of FIG. 7 .

At 802, a message is identified as suspicious. For example, it is identified in 508 that a sender of the message is similar to a trusted contact based on a measure of similarity of a sender of the contact with a trusted contact of a particular identified recipient of the message. An example of a trusted contact is a contact that has been previously identified by the recipient (e.g., included in an address book of the recipient) or is a contact with whom the recipient has had at least a minimum amount of positive engagement (e.g., having exchanged emails at least twice, and at least two weeks apart) without a recent “negative engagement” (e.g., recipient has not recently marked a message from the contact as spam). In some embodiments, the message is identified as suspicious if a sender of the message has not previously sent a message to a recipient identified in the message. In some embodiments, the message is identified as suspicious if a recipient identified in the message has not previously sent a message to the sender of the message. In some embodiments, the message is identified as suspicious if a spam detector, a virus detector, and/or a malware detector has detected that the message includes a spam, virus or malware.

In some embodiments, by basing the whether the message is suspicious on knowledge about trusted contacts of the specified recipient of the message, a message is only classified as suspicious and risky based on the likelihood that the recipient will confuse the sender with a trusted contact specific to the recipient. Otherwise, the risk may be marginal if the recipient does not know or trust the sender of the message since the sender is likely not impersonating someone that the recipient already knows. Thus a message is particularly dangerous if it is not from a trusted party, but the recipient thinks it is. In contrast, if the recipient knows that an email from an untrusted party is from an untrusted party, he or she is not as much at risk as he or she is not likely to feel compelled to comply with the requests or instructions in the message

At 804, the sender of the message is automatically classified. In some embodiments, classifying the sender includes identifying a classification/category of the sender. For example, a relationship classification/category of the sender with respect to the specified recipient of the message is automatically determined based on a property of an identifier of the sender (e.g., domain), previous message history between the sender and recipient, and/or other list or database (e.g., database of business contacts of the recipient). Examples of the classification of the sender include a college, a business partner, a friend/acquaintance, or unknown.

For example, if the sender is associated with the same domain as the recipient, then the sender is classified as a colleague classification. This classification may also be used if the email address of the sender is a known personal email address of a user with a colleague message address. This personal address may be determined using manual registration of such addresses by the account owner, as well as by identification of message traffic indicative of a work account being related to a personal account, such as having closely related display names and extensive forwarding of material from one account to the other. If the sender is a service provider or a client of an entity associated with the recipient, then the sender is classified as a business partner classification. This type of classification may be identified by detection of a sufficient volume of message traffic over time between the sender and the recipient, or from a database/list of recorded business contacts/relationships. In some embodiments, the sender is classified as a friend/acquaintance classification for a given sufficient volume of message traffic over time between the sender and the recipient but cannot be classified as a colleague or a business partner. If the sender cannot be classified as a colleague, business partner, or friend/acquaintance, the sender is classified as known/stranger.

In some embodiments, the sender of the message is automatically classified based on a list of trusted contacts tracked for the recipient (e.g., tracked using the process of FIG. 2 ). For example, a trusted contact in the stored list of trusted contacts may be associated with a classification identifier provided by a user and/or automatically determined. An identifier of the sender of the email may be utilized to locate a corresponding entry in the stored list of trusted contacts to identify its classification.

At 806, a manual classification of the sender of the message is requested from the specified recipient of the message. For example, before the message is fully provided to the recipient, a classification of the sender of the message is requested from the user in order to verify the recipient's believed classification of the sender as compared to the automatically determined classification. In some embodiments, the message is modified to change, remove, or obfuscate (e.g., remove attachment, remove hyperlinks, hide phone numbers, only retain a beginning portion of contents of the message and hide ending portion of the message, etc.) at least a portion of the message to prevent the recipient from having full access to the message prior to verification of the recipient's knowledge about the sender of the message. In some embodiments, the message is modified to include selection choices corresponding to the classification options (e.g., different selectable HTML hyperlinks included in the message and selection of a particular hyperlink option sends a request to the unique address of the hyperlink that can be detected by a server to identify which classification option was selected based on the unique address of the request corresponding to the selection option). In some embodiments, if a recipient replies to the message to the sender prior to providing the classification, the reply message is held/quarantined at a mail server until it is determined that it is safe to send the message. Another classification option is to identify the sender as a spammer or malware attacker. Selection of this classification may result in the removal of the email and blocking of future messages from the sender.

FIG. 8B shows an example of a modified message requesting manual classification of the sender of the message. Message 820 includes contents of the original message 822 as well as added selected choices 824 that requests the recipient to classify the sender of the message.

Returning to FIG. 8A, at 808, based on the response to the manual classification request, a security action is performed, if applicable. In some embodiments, if the manual classification response does not match the automatically determined classification, a security action is performed to warn the recipient about the mismatch and/or prevent the user from fully accessing or replying to the message. For example, the message may be deleted and replaced with a version of the message that has been modified (e.g., subject, sender display name, sender address, reply to address, and/or content of the message removed or modified with a warning indicator). In another example, the message may be deleted and quarantined for additional review by the recipient and/or an administrator. In some embodiments, in the event the sender of the message was correctly classified manually by the recipient and the automatic classification was incorrect, an opportunity is provided to add the sender of the message to the list of trusted contacts for the recipient and/or add an identifier of the sender (e.g., email address and display name) to an existing contact (e.g., as a secondary email address) in the list of trusted contacts. The sender may be added to the list of trusted contacts by the recipient, an administrator, or by the sender (e.g., by requiring the user to prove access to an account of an existing trusted contact).

FIG. 9A is a flowchart illustrating an embodiment of a process for requiring a sender of a message to verify an identity of the sender. The process of FIG. 9A may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 . In some embodiments, at least a portion of the process of FIG. 9A is performed in filtering the message in 506 and/or 510 of FIG. 5 . In some embodiments, least a portion of the process of FIG. 9A is performed in one or more steps of the process of FIG. 7 . For example, at least a portion of the process of FIG. 9A is performed in performing the first and/or second risk analysis of the process of FIG. 7 .

At 902, a message is identified as suspicious. For example, it is identified in 508 that a sender of the message is similar to a trusted contact based on a measure of similarity of a sender of the contact with a trusted contact of a particular identified recipient of the message. An example of a trusted contact is a contact that has been previously identified by the recipient (e.g., included in an address book of the recipient) or is a contact with whom the recipient has had at least a minimum amount of positive engagement (e.g., having exchanged emails at least twice, and at least two weeks apart) without a recent “negative engagement” (e.g., recipient has not recently marked a message from the contact as spam). In some embodiments, the message is identified as suspicious if a sender of the message has not previously sent a message to a recipient identified in the message. In some embodiments, the message is identified as suspicious if a recipient identified in the message has not previously sent a message to the sender of the message. In some embodiments, the message is identified as suspicious if a spam detector, a virus detector, and/or a malware detector has detected that the message includes a spam, virus or malware.

At 904, the message is prevented from being fully accessible by the specified recipient of the message. For example, at least a portion of the message is modified or removed. In another example, the message is quarantined and not delivered to the recipient.

At 906, an automatic reply to the message is sent requesting verification of an identity of the sender of the message.

This verification attempt may be utilized to identify good emails from accounts that are not trusted, but which are nevertheless associated with trusted persons. For example, if one executive's name is John Adams, and another executive receives an email from a John Adams—but not the same account as to which she has a trust relationship—then this is a potentially deceptive email—but also an email that is potentially from another account (such as the personal account) of the trusted person. The reply message includes the message “Your email triggered an alert. Have you sent emails to the recipient using another email address? If so, please click here. Otherwise, click here.” The first hyperlink (associated with the first occurrence of “here”) would lead to a website where the visitor enters his or her “other” email address (e.g., trusted contact address), and a verification email is sent to that address. That verification email contains a challenge value, such as a secret string of alphanumeric characters, that the recipient has to copy and paste into the site where the email address was entered. The second hyperlink takes the user to a site where he or she is offered to solve a CAPTCHA, associate a phone number (e.g., by sending an SMS challenge value to the phone number), or perform another action that attackers are typically unwilling to perform.

FIG. 9B shows an example of an automatic reply message requesting verification of an identity of the sender of the message. Message 920 informs the user that the sender's message has been quarantined and will not be delivered unless identity of the sender is established. Message 920 instructs the sender to forward the automatic reply message to a second message account (e.g., account of trusted contact) that the sender has previously used to communicate with the recipient and using the second account, forward again the forwarded message to a verification system for verification of the possession of the second account.

Returning to FIG. 9A, the automatic reply to the message may be utilized to detect spoofing attempts. For example, the automatic reply is sent to a system of the sender to request verification that the sender identified in the message actually sent the message. For example, at least two installations of message security systems, where a first installation is associated with a first entity and a second installation is associated with a second entity, the second system identifies receipt of an email originating with a sender associated with the first system. The second system then sends an inquiry to the first system, where the inquiry contains information related to the email. The first system determines whether the email associated with the inquiry was sent from the indicated apparent sender, and generates a response to the second system. If the second system receives a negative response, then the email is not delivered to the intended recipient, or if it has already been delivered, then it is either removed from the inbox or a notification is sent to the recipient, warning the recipient of the email. In addition, a notification may be sent to an administrator associated with the second system. In some embodiments, a notification is also sent to an admin associated with the first system. If, on the other hand, the response to the inquiry is a positive response, then the email is delivered to the recipient. If an email has more than one recipient within the second system, then it is delivered to each such recipient. Here, the first and second systems may access emails in different ways. For example, the first system may correspond to an outbound collector of emails and the second system to an OAUTH access of one or more email boxes. The first system may also be an appliance controlling or relaying emails, or be an OAUTH-enabled method to access the various mailboxes (including the sent folder) of one or more users. In some embodiments, all communications between the two security systems are encrypted and authenticated.

At 908, if the sender has provided a valid identity in response to the automatic reply in 906, the message is allowed to be fully accessible by the specified recipient. For example, if the user has provided an established position of an alternate trusted account that can be trusted (e.g., account of trusted contact) or has otherwise provided or proved an identity of the sender, the message is allowed to be fully accessible. Making the message fully accessible may include allowing the message to be delivered and accessed by the recipient with all of its original content. This may also cause the sender (e.g., sender email address) to be whitelisted or associated with an increased trust value (e.g., add to trusted contacts). In some embodiments, the provided full access message includes a warning, bringing to the attention of the recipient that this is an email from a potential stranger.

If the sender does not provide a valid identity in response to the automatic reply in 906, the message may remain unable to be fully accessible by the specified recipient of the message. In some embodiments, the message is indicated to an administrator and/or deleted.

In some embodiments, if the reply to the address of the message is identified or unknown to be unattended (e.g., not monitored by a recipient user), the message is provided to the recipient in a modified form and/or with a warning.

FIG. 10 is a flowchart illustrating an embodiment of a process for determining a change in historical reputation of a sender of a message. The process of FIG. 10 may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 . In some embodiments, at least a portion of the process of FIG. 10 is performed in filtering the message in 506 and/or 510 of FIG. 5 . In some embodiments, least a portion of the process of FIG. 10 is performed in one or more steps of the process of FIG. 7 . For example, at least a portion of the process of FIG. 10 is performed in performing the first and/or second risk analysis of the process of FIG. 7 .

At 1002, a long term measure of reputation associated with a sender of a message is determined. The long term measure of reputation may be for a specific address and/or domain of the sender. For example, long term measure of reputation is determined based on the amount of historical message traffic between the sender (or network domain of sender) and the recipient (or network domain of recipient). Large amounts of traffic may correspond to a high long term measure of reputation, unless there is a sufficient portion of the traffic that is flagged as undesirable (e.g., being spam, including virus/malware, etc.). Additionally, a long time period of traffic may correspond to a high long term measure of reputation, unless a sufficient portion is flagged as being undesirable. To the extent that it is available, a large open rate (e.g., the recipient opened the message) or a high response rate (e.g., whether replying to message or selecting links in message) also may correspond to a high long term measure of reputation, unless a sufficient portion is flagged as being undesirable. An example of a “sufficient” portion may mean that a fixed portion of the traffic, such as 2%. The long term measure of reputation may capture historical message traffic within several recent months. In some embodiments, when determining a long term measure of reputation for a domain, individual long term measures of reputation for accounts of the domain may be aggregated to determine the long term measure of reputation for the domain.

At 1004, a recent short term measure of reputation associated with the sender of the message is determined. The recent short term measure of reputation may be for a specific address and/or domain of the sender. The recent short term measure of reputation is determined using the same/similar factors as the long term measure of reputation but within a smaller time window. For example, the recent short term measure of reputation may capture historical message traffic within a day.

The recent short term measure of reputation may be low if a large portion (e.g., 5% of traffic within the time window) of message traffic between the sender (or network domain of sender) and the recipient (or network domain of recipient) is associated with complaints, spam detection, the detection of unwanted URLs, or unwanted attachments. An unwanted URL/attachment is one that is judged likely to be associated with risk, e.g., using a blacklist or an anti-virus scan. Complaints may correspond to users reporting an email as spam or phish, or placing it in a spam folder. Complaints can either be local (only a very small number of users, such as less than 1% of recipients, report the message) or pervasive (a greater portion of users report the email, e.g., more than 1%).

At 1006, changes in the recent short term measure with respect to the long term measure of reputation are detected and utilized to determine whether and/or how to filter the message. For example, if the sender is associated with a low (bad) long term measure of reputation (e.g., below a threshold) and a low (bad) recent short term measure (e.g., below another threshold), the message from the sender is identified as suspicious and filtered (e.g., blocked and/or modified with a warning). In some embodiments, if the sender is associated with a high (good) long term measure of reputation (e.g., above a first threshold) but low (bad) recent short term measure (e.g., below a second threshold), the message from the sender is identified as likely taken over by a malicious attacker. For example, the message may be filtered (e.g., blocked and/or modified with a warning), may require manual review by an administrator, or require an action by the sender (e.g., require sender to respond to a challenge) prior allowing delivery of the message (e.g., modified message with warning).

In some embodiments, let Ri be a reputation associated with a receiver, and for concreteness, assume that this corresponds to a numeric value between 0 and 1, inclusive. Let Bi be a recent short term measure of reputation associated with an email E received by the same recipient. For concreteness, this is also a value between 0 and 1, inclusive. Here, i is a number corresponding to the recipient. Further, let G be the long term measure of reputation associated with the email E, and may be a number between 0 and 100, for example. The value SUM(Bi*Ri)/G is computed, where SUM corresponds to adding the entries associated with all recipients of E. If SUM(Bi*Ri)/G >t1, where t1 is a first threshold, then a first action is taken. This action may be to block emails from the sender of E, remove E from the inbox of all recipients, and determine whether any of the users who appear to have opened E have had their computers corrupted or credentials stolen. This can be determined by asking the user, by scanning the user's machine, or by reviewing logs of incoming/outgoing traffic to the user's machine, where this review is preferably automated. Further, the action may involve increasing Ri by 10% for each user who filed a response Bi indicative of a threat. If SUM(Bi*Ri)/G<t2, where t2<t1 then the reputation Ri of each user who filed a response Bi indicative of a threat is decreased, e.g., by 5%. If the number of users filing a response Bi is indicative of a threat within a time T of receipt of the email E, then the email is considered to be associated with pervasive badness, otherwise local badness.

FIG. 11 is a flowchart illustrating an embodiment of a process for linking a secondary message account of a user. The process of FIG. 11 may be at least in part implemented on analysis server 102, gateway 110, and/or message server 106 of FIG. 1 .

At 1102, frequent forwarding of a message to an external message contact from an internal account is detected. For example, it is detected that a threshold number of messages have been forwarded to the same external contact for a user message account. For example, a member of an organization has an email address joe@organization.org, and a display name “Joe Schmoe.” This first member occasionally forwards calendar invites sent to him to an external account s123@gmail.com, which has a display name “J. Schmoe,” and it is detected that a threshold number of messages (e.g., email messages, calendar invitations, etc.) have been forwarded to s123@gmail.com.

At 1104, an inquiry regarding whether the external message contact is a secondary message of the user of the internal account is sent. For example, a message is sent to joe@organization.org asking “Is s123@gmail.com your email address? Click yes or no.”, where the words “yes” and “no” are hyperlinked.

At 1106, based on a response to the inquiry, forwarding of messages to the external contact is controlled. For example, if the user clicks on “yes” to the inquiry message sent in 1104, the system links the external message contact to the internal account (e.g., the external contact address, s123@gmail.com, is assigned the same trust level as that of an internal member of the organization) and future forwards to the external contact are allowed. If the user responds “no,” then the system may continue to observe further actions, such as forwarding of calendar invites, and if a second threshold number of such messages or invitations are detected, then the user is asked again or a notification is sent to an admin or the manager of the internal account, bringing the potential relationship to the attention of the manager. The “no” response may also disable forwarding of messages to the external contact.

In another example, a collection of users in the organization receive two emails; one from joe@organization.org and another from s123@gmail.com. If the collection of users is sufficiently large, such as at least five users in size, then it is unlikely that they would receive emails from two users with the same or similar display name if these two users do not correspond to the same person. In this case, at least one of the two email accounts is sent a message asking whether the two accounts correspond to the same person. Assume that the external account s123@gmail.com is sent the message “Is joe@organization.org your email address? Click yes or no.” If the user clicks yes then he is told that a code will be sent to joe@organization.org—the user is asked to email this same code from the account s123@gmail.com to confirm the linkage, or to paste the code into a webpage that he is taken to when clicking on “yes.” If the user clicks no and a transmission pattern suggesting a relation persists, then another message is sent, inquiring about the relationship, or a manager or admin is sent a notification.

In some embodiments, if a user indicates that two accounts are related, then the external account is preferably requested to sign up for protection of the external account (e.g., by providing the internal account system access (e.g., limited access) to the external account). If the user does not sign up for protection within a set amount of time (e.g., one week), traffic between the two accounts (e.g., joe@organization.org and s123@gmail.com) is filtered. This filter may be to block all such traffic, block certain types of such traffic such as calendar invites, delay such traffic, bring such traffic to the attention of the manager of the person, or some other action. This encourages enterprise users to link personal accounts with their work accounts to increase the protection of both accounts.

FIG. 12 is a flowchart illustrating an embodiment of a process for detecting an account take over. The process of FIG. 12 may be at least in part implemented on analysis server 102, gateway 110 and/or message server 106 of FIG. 1 .

At 1202, a rule to detect forwarding and removal/deletion of a message is configured for a message account. For example, after an enterprise has been secured by an email security system, one should preferably also secure perimeter accounts. One example of a perimeter account is the personal email address of an employee of the enterprise. Another example of a perimeter account is the personal or work account of a person associated with an employee of the enterprise, such as the spouse or babysitter of a person with an account at the enterprise. Other examples are the email address of a vendor associated with the enterprise and a personal email address of the vendor.

Enterprise accounts may be protected using one architectural approach, such as rewriting the MX records for the enterprise. The perimeter accounts may be protected using the same or a different architectural approach. For example, a user may grant an enterprise or another controlling entity authorization to access the user perimeter account (e.g., OAUTH access). The authorization may be a limited access to establish and utilize the rule. Enterprise accounts may be protected using a first collection of filters, e.g., filters that determine who all users are who commonly interact with a given account, and blocking any email that is considered unsafe. Perimeter accounts may either be protected in the same manner, or in a different manner. For example, perimeter accounts could simply be protected by determining whether they are likely to have been ATOed (i.e., taken over) by an attacker; with no traffic other than likely ATO threats being blocked; and without determining who are commonly interacting with the perimeter account.

A perimeter account is determined to have a heightened risk of having been ATOed if copies of some emails known to have been sent to the account are found by the security system to have been immediately forwarded to another email address. This can be determined in several ways. One way is if an email sent by a protected enterprise account is found not to be delivered to the inbox of the perimeter account, but found in the sent box of the perimeter account. Here, the security system can inject the message from the protected enterprise system, and the message can be empty or contain a legitimate-looking text. If an injected message is found to be delivered in the inbox of the perimeter account, then the security service deletes it so that the end user is not confused. If it is found to be automatically forwarded by being found in the sent box, then the system determines that the risk associated with the perimeter account is increased. The risk is very high if it is found that messages are selectively forwarded, and that those that are forwarded are not delivered to the inbox. This can be achieved by setting a simple sender-specific rule, and is commonly done by attackers having ATOed an account. The security system detects that messages are selectively forwarded if at least one message is found to be automatically or very quickly forwarded, whereas another message is delivered into the inbox of the perimeter account. A perimeter account can also be found to be associated with a high risk if its communication behavior suddenly changes, e.g., an unusual number of messages are sent within a short period of time, or high-risk keywords are found in outgoing messages. A perimeter account can be protected against some classes of abuse by active filtering. Such filtering can be the same as what is used for the enterprise accounts that are protected, or use some of the filter rules, and may also use additional filter rules not suitable to an enterprise. For example, an enterprise may filter out any commercial offer emails, whereas users of perimeter accounts may want these; at the same time, an enterprise account might not filter out messages with wire instructions whereas a perimeter account may have filters associated with it that flag any such messages and add a warning to them, since such messages are commonly used by scammers, but are also in common enterprise-to-enterprise communications.

At 1204, triggering of the rule is detected and the associated message account is secured. For example, when the rule is triggered and a threat is detected for the account, then all messages from the account to other accounts of a protected enterprise are treated as being high-risk. This results in modification or blocking of at least a portion of messages. For example, it may result in blocking of all potentially risky attachments, quarantining all messages until they have been confirmed by the sender, after the sender is challenged using a secondary channel such as SMS, or adding warnings to such incoming messages.

FIG. 13 is a flowchart illustrating an embodiment of a process for detecting forwarding of a message. The process of FIG. 13 may be at least in part implemented on analysis server 102, gateway 110, and/or message server 106 of FIG. 1 . The detection of message forwarding may be helpful in the detecting of account take overs by a malicious attacker.

At 1302, a message to be sent is received. For example, an email message to be sent is received at an email server.

At 1304, a unique subdomain is added to the sender address of the message and the message is sent. For example, if the protected organization corresponds to a domain organization.org, and a user Bob has an account Bob@organization.org, and Bob wishes to send an email E to Alice at Alice@service.com, then an agent associated with the mail transfer agent (MTA) of organization.org will insert the unique subdomain in the sending address. If the unique subdomain is 67H7kT79q, then the sender of the email will be changed to Bob@67H7kT79q.organization.org. The display name for Bob can remain the same as it normally is, which may be “Bob Lastname,” or it may be augmented with the unmodified email address to become “Bob Lastname <Bob@organization.org>.”

At 1306, a confirmation of the receipt of the message is detected. For example, as the email E is transmitted to the message receiving service, the message receiving service will verify the DMARC record of the sender, causing a request for 67H7kT79q.organization.org to be generated to the DMARC provider on record for organization.org. Assuming 67H7kT79q.organization.org is valid, the provider will respond positively. Thus, it is detected that email E was received by the mail service provider associated with service.com.

At 1308, a forwarding of the message is detected. Based on this detection, message filtering and/or security action may be performed. For example, if Alice, the recipient of the email, has configured her email account Alice@service.com to automatically relay or forward emails (whether generally or selectively) and E as a result gets forwarded to service2.com, then service2.com, too, will make an inquiry to the DMARC provider of organization.org. By detecting the second DMARC inquiry quickly (e.g., within a threshold amount of time) after the first DMARC inquiry, automatic forwarding of the message is able to be detected. As a result, the DMARC provider will be able to monitor how the message E is (or is not) forwarded or relayed. Currently, such reports are generated on a daily basis, but as they become more frequent, the value of such information will increase. For each party communicating with users within organization.org, the DMARC provider, or an entity associated with it, will therefore be able to build a profile of expected behavior. These may change over time, e.g., if Alice goes on vacation and sets some messages to be forwarded, or if Alice's account gets taken over by a criminal who sets forwarding in order to steal messages from Alice and inserts himself into a conversation between Alice and Bob.

Whereas the DMARC provider or associated entity cannot determine with certainty whether a change in forwarding behavior is acceptable or not, it is helpful to flag any changes. It is also possible to record all the common forwarding behaviors for a user or associated domain, and determine when a new forwarding behavior is seen. It is furthermore practical to maintain a list of forwarding entities that are associated with high risk. Based on the presence of a forwarding change, and the nature of this, the system takes a security action. In one embodiment, this security action involves generating a challenge and sending it to the party communicating with the protected user, in this case causing a message to be sent to Alice@service.com. The message may require the recipient to click on a hyperlink to avoid further security actions—this enables the detection of IP addresses for the recipient, which in turn can be used to identify risk. Another security action is to modify messages sent from the flagged user to incorporate a warning, or remove any high-risk elements such as attachments of certain types associated with malware risk. Yet another security action is to modify messages sent to the flagged account, blocking transmission of sensitive documents. For example, any document appearing to comprise PII or other sensitive information can be automatically removed or redacted.

If the DNS lookup service were to always accept the first request for a DMARC related subdomain/domain lookup, but reject any consecutive lookups, and the email service is configured accordingly, this would result in the automated blocking of automated relaying of messages.

An alternative approach to rewriting sender addresses on all outbound emails for a protected domain is to provide a unique Mail From domain for all outbound emails, using a similar sub-domain approach for each message. For example the Mail From address might look like bounces@67H7kT79q.organization.org. In this case the SPF lookup done by the mail service provider, service.com, would look for an SPF record at the sub-domain 67H7kT79q.organization.org. Organization.org would need to create DNS TXT records for each unique sub-domain it uses in the Mail From field. This would allow the messages to pass SPF at service.com and pass the DMARC SPF alignment check at service.com. If the email is then forwarded to service2.com, the same SPF check by service2.com against 67H7kT79q.organization.org would fail. A record of the message with this unique Mail From domain would appear in the DMARC report from service.com with a passing result and in the DMARC report from service2.com with a failing result. Thus, DMARC analysis for organization.org would be able to detect the act of forwarding for this message.

FIG. 14 is a flowchart illustrating an embodiment of a process for detecting message bomb attacks. The process of FIG. 14 may be at least in part implemented on analysis server 102, gateway 110, and/or message server 106 of FIG. 1 . The detection of message forwarding may be helpful in the detecting of account take overs by a malicious attacker.

At 1402, a baseline message traffic measure is determined for each message sending entity. The message sending entity may be an individual sender for an organization (e.g., for Google Gmail, Facebook, and organizations that allow signups to newsletters on their websites) that does not exercise strict control over its membership, while the sending entity may be an entire organization for organizations with tight control over membership (e.g., bank entity, where it is not possible for anybody to send to a selected account on behalf of the organization, or cause a transmission to a selected account on behalf of the organization). A list of message sending entities that have sent messages to users of an organization to be protected may be identified by tracking on a per-entity basis the amount of messages sent over a specified period of time. If a message sending entity has sent more than a threshold quantity of messages (e.g., at least three messages within two months), and where recipients have not marked these message as spam more than a spam threshold (e.g., less than 1%), the sending entity is included in a whitelist of trusted sending entities.

At 1404, it is determined whether a message account is under message bomb attack (e.g., message denial of service attack). In some embodiments to detect the attack, sudden spikes of incoming traffic are identified. For example, if the hourly volume for a target organization has never exceeded 800,000 emails over the last six months, then the threshold may be set to correspond to the same number of incoming emails in one minute, e.g., a 60-time increase compared to the historical limit. If at any time this threshold is exceeded, then message blocking is triggered. An alternative approach is to determine the number of emails sent from entities who are not whitelisted within a given time period. Assume the historical maximum is 20,000 for a minute, meaning that the system has not received more than 20,000 emails within one minute from senders who are not on the whitelist. Then the system may use a threshold of 100,000 emails from entities not on the whitelist for one minute, corresponding to a five-fold increase compared to the previous maximum. Exceeding this threshold would trigger the message blocking. It may be useful to be able to trigger the blocking system manually, or in reaction to another organization being under attack, or any combination of such triggers.

If it is determined that the message account is under attack, at 1406, message blocking is triggered. For example, when message blocking is triggered, all messages received from entities not on the whitelist are rejected or otherwise not delivered, until a second condition is met. This second condition may correspond to triggering the lifting of the blocking, and may be associated with the volume of emails falling below a threshold considered acceptable.

FIG. 15 is a flowchart illustrating an embodiment of a process for providing a secure message interaction interface region. The process of FIG. 15 may be at least in part implemented on analysis server 102, gateway 110, and/or message server 106 of FIG. 1 . The detection of message forwarding may be helpful in the detecting of account take overs by a malicious attacker.

At 1502, a received message is verified. For example, it is determined in 504 of FIG. 5 that a sender of the message exactly matches a trusted contact, or in 508 of FIG. 5 it is determined that the sender of the message is not similar to a trusted contact. In some embodiments, the received message is verified as passing DMARC verification.

At 1504, a secure message interaction interface region is provided in association with a display of the received message to the recipient of the message. Often a message recipient may be tricked into performing unsafe actions instigated by a message that is a part of an impersonation attack. By providing on a message client (e.g., email client) or a user interface of a message service (e.g., web email interface) a special display region that can only display authorized information and/or actionable elements of messages that have been verified as authentic (e.g., pass DMARC verification), a user may be conditioned to utilize the special display region to perform actions or verify authenticity of a message for highly sensitive content/messages rather than relying on a body of a message that can be configured as desired by a malicious attacker.

For example, an email sender can include information relating to the actionable elements of the secure message interaction interface region in a message header, such as an X-header, where such headers are digitally signed before the message is transmitted. Alternatively, an online service can maintain an association between whitelisted senders and sources of actionable elements. In yet another implementation, the message may contain a purpose-specific MIME part, in which a list of elements to be displayed in the secure area and their metadata could be included within the body of the email message.

In some embodiments, the secure message interaction interface region (i.e., secure display area) includes a representation of the sender, such as a photo or a logo, where this representation has been vetted and associated with the sender upon registration of the sender in the system. The representation may be stored by a message service provider, requested from a third-party resource on demand, or attached to the message in a header or content portion, and digitally signed by the sender before transmission. In addition, the secure display area may also preferably comprise at least one actionable element, such as a link to a website or a handle associated with an attachment, allowing the user to access a resource associated with the actionable element. Information associated with such actionable elements may be included as part of the message, whether in the header or content portion or obtained from a source associated with the sender. In one embodiment, the material associated with the actionable element is stored by the message service provider and provided to two or more recipients who receive an email from the sender, where the message indicates that the stored actionable element should be displayed in the secure display area.

In some embodiments, at least some of the actionable elements are customized for one or more users. One example customization of actionable material is the selection of what actionable elements are made available to one user, as opposed to another. For example, one user may be provided actionable elements corresponding to (1) a hyperlink to a checking account, (2) a hyperlink to a mortgage account, and (3) a link associated with a secure message sent to the user; whereas another user may be provided actionable elements corresponding to (1) a hyperlink to a savings account, (2) a late credit card bill payment alert, and (3) a request to verify whether a credit card was used in a specified location for a specified purchase. Some types of actionable material are static, such as a link to a savings account, whereas other types are dynamically generated as the secure display area is rendered. For example, a user receiving a message that is associated with a secure display area that comprises a request to verify whether a credit card was used in a specified location for a specified purchase—and who verifies this transaction—can then come back to view the secure display area, at which time the request to verify the transaction is not included as an actionable element.

For example, a sender may send a message to a customer, requesting the user to accept new terms of service, but by the time the user reads the message and displays the secure messaging area, there is an account alert for the user, warning the user of recent activity. The user would be provided an actionable element relating to this warning. This may be made possible by a real-time lookup of actionable elements at the time of rendering of the secure display area. A second example form of customization relates to the content of the actionable elements. For example, these may comprise deep links allowing a user to access his or her account directly, if it is determined that he or she is already authenticated on the device displaying the secure display area; or that leads to a login portal otherwise, where after positive authentication, the user is sent to a customized location.

In addition to providing convenient and potentially real-time actionable items in the secure display area (e.g., the activation or use of which would typically entail the user being directed away from the email service or chrome of the email provider), another way to make the secure display area useful for message recipients to regularly reference and use is to use it to display information of interest to the recipient, such as an account balance or package delivery date for a package in transit shipped by the sender of the authenticated message.

The use of customization may provide both convenience benefits and security benefits to users, and the placement of the actionable elements in the secure display area provides security since it conditions users only to act on elements that have been verified to be associated with trusted senders. An important idea in this context is that by making access to sender-associated resources of interest to the recipient (e.g., pointed to by the links displayed in the secure area) more convenient (e.g., through use of the MUA chrome-based secure display area either conveniently located visually for the end user and/or capable of displaying customized near-real-time content of interest to the recipient), message recipients are more likely to use it and rely upon it. With convenient and increasingly frequent interactions made secure, overall safety and protection against fraud is improved.

In some embodiments, the list of actionable items to be displayed in the secure display area is generated through a function which combines both real-time actionable items fetched from a system specified by the authenticated sender with the static actionable items carried within the email message (e.g., display-time actions and message send-time actions, known at the time the message is composed and sent). In some embodiments, information pulled in real-time from the sender's systems, such as a recipient's checking account balance, in the case of the sender being a bank, is included in the secure display area. To facilitate this, the recipient's account number (or a one-time use, limited-duration, or one-function-only identifier that maps to the recipient's account to allow a fetch of the current balance but nothing else) may be included in the message via a header or inclusion in the body. Imposters would not be able to include a working cryptographic nonce nor would their email pass the authentication tests required for the rendering of the secured display area. In some embodiments, in conjunction with the MUA operator (e.g., email provider) and the sender, certain compelling offers are provided in the secure display area, some of which could be made exclusive to the secure display area. In some embodiments, in the situation where a message is from a logistics/shipper, includes a tracking number, and is verified to be authentic, the secure display area shows package tracking information (e.g., location, timing, anticipated delivery time, etc.). Furthermore, in situations where a message's sender cannot be verified and/or there is reason to believe its contents are not trustworthy, the operator of the mail user agent can intentionally disable any actionable links present within the message body.

In some embodiments, the rendering of the secure display area is conditional on the email passing at least one security test, and in one embodiment conditional on a user action, such as clicking on or mousing over a location or element associated with the rendering of the secure display area. This location could, for example, be the sender email address or an icon displayed in the chrome of the message.

Alternatively, if the message is the sole message being displayed in full (e.g., not a view of a user's mailbox in which a summary is shown for multiple messages at once), the secure display area could be shown immediately beneath the message's header information (e.g., the “To,” “From,” date, and subject fields). The benefit may be that no user action is required to cause it to be displayed. In this situation, the secure area could contain a message to the effect of “no secure actions were found” if the message failed authentication tests. This would represent an additional signal to the recipient that the message may not be trustworthy.

FIG. 16A shows example components of a message and FIG. 16B shows a secure display area of the message. Text and content of the message are not shown to simplify the example and illustrate the embodiment clearly. Email 1601 includes a displayed from field 1602, a displayed to field 1603, a displayed content field 1604, and an optional security indicator 1605 that is not displayed, and which in one embodiment comprises a digital signature on at least portions of the email 1601. Examples of optional security indicator 1605 include information associated with where the email was sent from, such as the IP address, the sending server, the path of transmission, or header information relating to the carrier used by the sender or the computer device used by the sender. As a result of the recipient of the email 1601 interacting with a portion of the email, such as from field 1602, a secure display area is generated and rendered as shown in FIG. 16B. Secure display area 1606 is generated and rendered in response to the user action taken by the recipient of email 1601. Secure display area 1606 comprises a representation image of the sender 1607, an actionable element 1608, and an actionable element 1609. Examples of the actions performed by selecting actionable elements 1608 or 1609 include selection of hyperlink(s), opening of attachment(s), initialization of secure user messaging, etc.

Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive. 

1. A method, comprising: determining, using one or more computer processors of a network device, a measure of risk associated with a received message, wherein an address of a sender of the received message is not included in a list of at least one trusted contact of a recipient of the received message; based at least in part on the combined measure of risk associated with the received message, performing, by the network device, a verification action by automatically providing an inquiry message to a client device of one of the recipient or the sender, wherein the inquiry message requests a response to be provided; and performing a security action based on the response responsive to the inquiry message.
 2. The method of claim 1, wherein the inquiry message is sent to the recipient of said received message.
 3. The method of claim 2, wherein the inquiry message requests the recipient of said received message to classify the sender of said received message.
 4. The method of claim 3, wherein the inquiry message includes an obfuscated version of said received message.
 5. The method of claim 1, wherein the inquiry message is sent to the sender of said received message.
 6. The method of claim 5, wherein the inquiry message requests one or more of: verification of an identity of the sender of said received message, and the sender of said received message to forward the inquiry message to an alternate account of the sender of said received message and further forward the forwarded version of the inquiry message from the alternate account to a specified destination.
 7. The method of claim 1, wherein the measure of risk comprises a combined measure of risk, wherein determining the combined measure of risk further comprises: determining at least one of a measure of trust or a measure of spoofing risk associated with the sender of the received message; determining a measure of similarity between an identifier of the sender of the received message and an identifier of at least one trusted contact of a recipient of the received message; combining the measure of similarity with at least one of the measure of trust or the measure of spoofing risk to at least in part determine the combined measure of risk.
 8. The method of claim 7, wherein determining the measure of similarity includes sorting elements of the identifier of the sender and sorting elements of the identifier of the at least one trusted contact of the recipient of said received message.
 9. The method of claim 7, wherein determining the measure of similarity includes determining a string similarity measure between the identifier of the sender and the identifier of the at least one trusted contact.
 10. The method of claim 7, wherein determining the measure of similarity includes detecting substitution characters in the identifier of the sender.
 11. The method of claim 7, wherein the measure of spoofing risk associated with the sender of said received message is determined and the spoofing risk is based at least in part a message validation policy associated with a network domain of the sender of said received message.
 12. The method of claim 1, wherein the at least one trusted contact of the recipient was automatically identified at least in part by analyzing previous messages sent and received by the recipient of said received message.
 13. The method of claim 1, wherein the at least one trusted contacts of the recipient was identified at least in part by analyzing previous messages sent and received by a plurality of different message accounts of a same network domain of the recipient of said received message.
 14. The method of claim 1, further comprising: determining a first measure of reputation associated with the sender of said received message; determining a second measure of reputation associated with the sender of said received message, wherein the first measure of reputation is associated with a longer timer period than the second measure of reputation; and detecting a change in the second measure of reputation in light of the first measure of reputation, wherein said received message is filtered based at least in part on the detected change.
 15. The method of claim 1, further comprising determining a measure of control of a network domain of the sender of said received message, wherein said received message is filtered based at least in part on the measure of control of the network domain.
 16. The method of claim 1, wherein the at least one trusted contacts of the recipient was identified based at least in part on contacts included an address book of the recipient of said received message.
 17. A system, comprising: a processor of a network device, the processor configured to: determine a measure of risk associated with a received message, wherein an address of a sender of the received message is not included in a list of at least one trusted contact of a recipient of the received message; based at least in part on the measure of risk associated with the received message, perform a verification action including by automatically providing an inquiry message to a client device of one of the recipient or the sender, wherein the inquiry message requests a response to be provided; and perform a security action based on the response responsive to the inquiry message; and a non-transitory memory coupled to the processor and configured to provide the processor with instructions.
 18. The system of claim 17, wherein the inquiry message requests the recipient of said received message to classify the sender of said received message.
 19. The system of claim 17, wherein the inquiry message is sent to the sender of said received message and the inquiry message requests verification of an identity of the sender of said received message.
 20. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions that, when executed, cause one or more processors of a network device to: determine a measure of risk associated with a received message, wherein an address of a sender of the received message is not included in a list of at least one trusted contact of a recipient of the received message; based at least in part on the measure of risk associated with the received message, perform a verification action including by automatically providing an inquiry message to a client device of one of the recipient or the sender, wherein the inquiry message requests a response to be provided; and perform a security action based on the response responsive to the inquiry message. 